This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
Actually, we've done that already as a quick pre-test. We had 1.5GB discussion database on a Domino8 DB/2 enabled server, and the views opened pretty fast. We don't care about unread marks, since we disable them always, and use our own logic to implement unread marks (including read and edit counters).
The immediate performance benefits of using a DB/2 database are:
1) Views will be indexed faster (this is actually quite a common problem in big ((>1GB or >100000 documents) Domino .NSF databases)
2) You can substitute some LotuScript/Java/@Formula code into native DB/2 inner joins, those will work much faster than joining each record by LotuScript/Java/@Formula language. However, not all joins can be substituted into native DB/2 joins, especially superrelational joins (since SQL doesn't support them (for example joining a certain word in a rich text field with some other field in another database, or joining different fields of different databases by some complex logic inluding lots of "if" and "case" etc... branches)).
Feedback response number WEBB77SNEQ created by ~Richard Minnitherlen on 10/08/2007